-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize for timer timeout extension #184
Conversation
a500499
to
ff0a0de
Compare
@cmeissl The CI issues are fixed on master, please rebase |
d04c127
to
44b25e1
Compare
@cmeissl try again |
a733023
to
a21bc53
Compare
The CI failed because the version (latest) of |
bbee61f
to
f7ed219
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #184 +/- ##
==========================================
+ Coverage 85.63% 85.92% +0.28%
==========================================
Files 13 14 +1
Lines 1852 1989 +137
==========================================
+ Hits 1586 1709 +123
- Misses 266 280 +14
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
add benchmarks specifically targeting the use-case of extending a timer by removing and re-registering
in case we constantly extend the same timer the head might already point to the timer we want to cancel. in this case we can directly remove the timer to reduce building up the heap unnecessarily.
it is more likely an older timeout gets canceled and replaced. reversing the search might yield some performance improvement in this case
f7ed219
to
24a4544
Compare
@notgull I had to downgrade a few other deps, but the CI is now green finally! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
No description provided.